Authentication manager

ABSTRACT

Disclosed are various embodiments for an authentication manager. In one embodiment, the authentication manager performs an identity verification on a network site. The authentication manager determines that a particular portable data store is present in the client computing device, and then reads a security credential from the particular portable data store. The authentication manager automatically sends data encoding the security credential to the network site.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to,co-pending U.S. patent application entitled “AUTHENTICATION MANAGER”filed on Jul. 3, 2014 and assigned application Ser. No. 14/323,779,which is a continuation of, and claims priority to, co-pending U.S.patent application entitled “AUTHENTICATION MANAGER” filed on Aug. 12,2009 and assigned application Ser. No. 12/539,886, which issued on Jul.8, 2014 as U.S. Pat. No. 8,776,214, all of which are incorporated hereinby reference in their entireties.

BACKGROUND

Many web sites require users to log in with a username and password sothat the users may be securely identified. Users, however, often forgettheir username and/or password and/or specify the same username and/orpassword for multiple web sites. Managing tens or even hundreds ofusernames and passwords is a major cause of pain for users and resultsin excessive abandonment rates where users simply fail to sign up for anew service if it requires a new account.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following drawings. The components in the drawings arenot necessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views.

FIG. 1 is a drawing of a networked environment according to variousembodiments of the present disclosure.

FIGS. 2-4 depict examples of network pages rendered by a browserexecuted in a client in the networked environment of FIG. 1 according tovarious embodiments of the present disclosure.

FIGS. 5 and 6 are flowcharts illustrating examples of functionalityimplemented as portions of an authentication manager executed in aserver in the networked environment of FIG. 1 according to variousembodiments of the present disclosure.

FIG. 7 is a schematic block diagram that provides one exampleillustration of a client employed in the networked environment of FIG. 1according to various embodiments of the present disclosure.

DETAILED DESCRIPTION

Many network sites, such as web sites, use passwords and/or usernamesand passwords in order to authenticate user accounts. Although passwordsmay be a strong security credential when used properly, they are oftenmisused. For example, a user may set a relatively weak password, such asa word from a dictionary or a password that is otherwise easy to guess.A user may also set the same password for multiple accounts acrossmultiple network sites and with different security requirements. Thus,if one account is compromised, all other accounts using the samepassword are also vulnerable. Moreover, through a practice known as“phishing,” a user may inadvertently provide a password to a fraudulentnetwork site that resembles a legitimate network site.

Thus, many problems associated with using passwords as a securitycredential are caused by humans being unable to process the type of datathat passwords represent. Good passwords are often random and long,which makes them hard to remember. Passwords are often not a singlechunk of information and can stretch the limits of human working memory.The system disclosed herein largely separates the user from thepassword, thereby resolving many of the issues. For example, the systemmay automatically generate a unique, strong password for each networksite, using characters selected from the entire set of charactersacceptable by the network site. In ordinary use, the user may not needto know the password for the network site. Further, the system may beconfigured to verify the identity of a network site before providing apassword to the network site, thereby thwarting most phishing schemes.In the following discussion, a general description of the system and itscomponents is provided, followed by a discussion of the operation of thesame.

With reference to FIG. 1, shown is a networked environment 100 accordingto various embodiments of the present disclosure. The networkedenvironment 100 includes a client 103 that may be in data communicationwith servers 106, configuration file server 109, and remote data server112 by way of a network 115. The network 115 includes, for example, theInternet, intranets, extranets, wide area networks (WANs), local areanetworks (LANs), wired networks, wireless networks, or other suitablenetworks, etc., or any combination of two or more such networks. Theclient 103 may also be in data connection with a portable data store 118by way of, for example, a local interface, data bus, or another network115.

The client 103 may comprise, for example, a computer system such as adesktop, laptop, or other computer system. The client 103 may alsocomprise personal digital assistants, cellular telephones, set-topboxes, or other systems with like capability. Further, the client 103may also comprise any device that is network capable that maycommunicate with the servers 106, 109, 112 over the network 115 toperform various functions. Such clients 103 may comprise, for example,processor-based devices having processor circuits comprising a processorand a memory.

The client 103 may be configured to execute various applications such asa browser 121, an authentication manager 124, and/or other applications.The browser 121 may be executed in a client 103, for example, to accessand render network pages, such as web pages, or other network contentserved up by the server 106 and/or other servers. The authenticationmanager 124 may be executed to manage usernames, passwords, private andpublic keys, certificates, and/or other security credentials. In someembodiments, the authentication manager 124 runs as a plug-inapplication to the browser 121. In other embodiments, the authenticationmanager 124 may be a standalone application that interfaces with thebrowser 121 and/or other applications requiring management ofauthentication. The client 103 may be configured to execute applicationsbeyond browser 121 and authentication manager 124 such as, for example,e-mail applications, instant message applications, and otherapplications.

The client 103 includes a data store 127, and potentially other datastores, which may comprise data and applications configured to provideaccess to the data. The data store 127 may be used to store account data130, certificate trust data 133, and/or potentially other data. Accountdata 130 may include, for example, security credentials used to accessvarious network sites or network pages, information regardingauthentication endpoints, and/or other information. In variousembodiments, account data 130 may be stored in an encrypted format.Certificate trust data 133 may describe trusted certificate authoritiesthat issue digital certificates used by network sites. Certificate trustdata 133 may comprise, for example, public keys associated with thetrusted certificate authorities. The public keys may be used to validatethe digital signature of a trusted certificate authority on a digitalcertificate.

The server 106 may comprise, for example, a server computer or likesystem. The server 106 may represent multiple servers arranged, forexample, in one or more server banks or other arrangements. Such servers106 may be located in a single installation or may be dispersed amongmany different geographical locations. For purposes of convenience, theserver 106 is referred to herein in the singular. However, in oneembodiment, the server 106 represents a plurality of servers arranged asdescribed above.

The server 106 is configured to execute various applications such as,for example, a network page server 136, an account creation endpoint138, an authentication endpoint 139, and other applications. The networkpage server 136 is configured to serve up network pages, such as webpages, and other files from the server 106 to various clients 103. Thenetwork page server 136 may be configured to send network pages byhypertext transfer protocol (HTTP), hypertext transfer protocol secure(HTTPS), or some other protocol. The network page server 136 may employencryption using, for example, secure sockets layer (SSL), transportlayer security (TLS), and/or some other method. Non-limiting examples ofnetwork page servers 136 include Apache™ HTTP Server, Microsoft®Internet Information Services, and other server applications.

The network page server 136 may be configured to serve up one or morenetwork sites 140. Such a network site 140 is said to be hosted by thenetwork page server 136. A network site 140 may include a set of networkpages and/or files associated with a domain name, such as a canonicalname, and a directory, such as a root directory (i.e., “/”) or someother directory. Each network site 140 may be associated with distinctconfiguration settings in the network page server 136, while otherdefault configuration settings may be shared across network sites 140.

The account creation endpoint 138 may comprise a network page and/orsoftware configured to facilitate creation of one or more accounts forone or more users at a client 103 for one or more network sites 140. Invarious embodiments, the authentication manager 124 communicates withthe account creation endpoint 138 through the network page server 136.To this end, the account creation endpoint 138 may be a plug-in or othermodule of the network page server 136, a script or other softwareembedded within a network page or otherwise within a network site 140and executed by way of an interpreter or a common gateway interface, oraccessed in some other way through the network page server 136. In otherembodiments, the account creation endpoint 138 may be a serverapplication executing on the same or a different server 106 as thenetwork page server 136.

The authentication endpoint 139 may comprise a network page and/orsoftware configured to facilitate authentication of a user at a client103 for one or more network sites 140. In various embodiments, theauthentication manager 124 communicates with the authentication endpoint139 through the network page server 136. To this end, the authenticationendpoint 139 may be a plug-in or other module of the network page server136, a script or other software embedded within a network page orotherwise within a network site 140 and executed by way of aninterpreter or a common gateway interface, or accessed in some other waythrough the network page server 136. In other embodiments, theauthentication endpoint 139 may be a server application executing on thesame or a different server 106 as the network page server 136.

The server 106 includes a data store 142 and potentially other datastores, which may comprise data and applications configured to provideaccess to the data. The data store 142 may be used to store networkpages 145, configuration files 148, account data 151, certificate data154, and/or potentially other data. Network pages 145 may include thenetwork pages and/or files served up for the network sites 140 hosted bythe network page server 136. Configuration files 148 may include one ormore security credential specifications and/or describe an interface ofone or more account creation endpoints 138 and/or authenticationendpoints 139. Account data 151 comprises security credentials and/orother data associated with users of one or more network sites 140.Certificate data 154 comprises digital certificates that may be used bythe network page server 136, the authentication endpoint 139, and/orother applications on the server 106 to identify a network site and/orencrypt data.

The configuration file server 109 may comprise, for example, a servercomputer or like system. The configuration file server 109 may representmultiple servers arranged, for example, in one or more server banks orother arrangements. Such configuration file servers 109 may be locatedin a single installation or may be dispersed among many differentgeographical locations. For purposes of convenience, the configurationfile server 109 is referred to herein in the singular. However, in oneembodiment, the configuration file server 109 represents a plurality ofservers arranged as described above.

The configuration file server 109 includes a data store used to storeconfiguration files 157 and potentially other data. The configurationfiles 157 may include one or more security credential specificationsand/or describe an interface of one or more account creation endpoints138 and/or authentication endpoints 139. The configuration file server109 may be, for example, a system configured to provide configurationfiles 157 corresponding to a plurality of servers 106. The configurationfile server 109 may be operated, in some cases, by a third party. Insome embodiments, configuration files 157 may correspond toconfiguration files 148 stored on a server 106.

The remote data server 112 may comprise, for example, a server computeror like system. The remote data server 112 may represent multipleservers arranged, for example, in one or more server banks or otherarrangements. Such remote data servers 112 may be located in a singleinstallation or may be dispersed among many different geographicallocations. For purposes of convenience, the remote data server 112 isreferred to herein in the singular. However, in one embodiment, theremote data server 112 represents a plurality of servers arranged asdescribed above.

The remote data server 112 includes a data store used to store accountdata 160 and potentially other data. The account data 160 may include,for example, security credentials used to access various network sites140 or network pages 145, or to track user context across such networksites 140 or network pages 145; information regarding authenticationendpoints; and/or other information. In various embodiments, accountdata 160 may be stored in an encrypted format. The account data 160 maybe, for example, a mirror of account data 130 for one or more users.

The portable data store 118 may comprise, for example, a universalserial bus (USB) flash storage device, a solid-state storage device, aportable hard disk, a floppy disk, an optical disc, and/or otherportable storage devices. In various embodiments, the portable datastore 118 may include a processor circuit comprising a processor and amemory. In other embodiments, the portable data store 118 may merelyconsist of a storage medium. The portable data store 118 may beremovably attached to the client 103 in some embodiments.

The portable data store 118 may be configured to store account data 163.The account data 163 may include, for example, security credentials usedto access various network sites 140 or network pages 145, informationregarding authentication endpoints 139, and/or other information. Invarious embodiments, the account data 163 may be a mirror of the accountdata 130. In other embodiments, the account data 163 may take the placeof account data 130. The account data 163 may be stored in an encryptedformat. To this end, the portable data store 118 may include a device(e.g., a fingerprint scanner or other biometric recognition device, apin pad, etc.) used to authenticate a user in order to provide access tothe data on the portable data store 118, such as account data 163; or itmay include hardware and/or software to permit a user to enter apassword and/or decryption key in order to provide access to the data onthe portable data store 118. Additionally, in some embodiments, theauthentication manager 124 may be stored on the portable data store 118and executed in the client 103, for example, when the portable datastore 118 is attached to the client 103.

Next, a general description of the operation of the various componentsof the networked environment 100 is provided. To begin, a user mayinstall authentication manager 124 onto the client 103 and preconfigurethe operation of the authentication manager 124 for existing accountsassociated with network sites 140. For example, the user may provide tothe authentication manager 124 existing security credentials such as,for example, usernames, passwords, security keys, certificates, and/orother security credentials along with identifying information for thenetwork sites 140 and/or uniform resource locators (URLs) associatedwith the security credentials. The user may also configure a securitycredential such as, for example, a username, password, biometricidentification, etc. for the authentication manager 124 so that thesecurity credentials may be encrypted or otherwise protected from use orview on client 103 without the authorization of the user.

The account information may be stored by the authentication manager 124in account data 130 on the client 103 and/or at some other location. Forexample, the authentication manager 124 may back up the accountinformation to account data 160 located on the remote data server 106,account data 163 located on in the portable data store 118, and/oranother location. In some embodiments, the authentication manager 124may not store the account information on the client 103 at all and mayonly use other locations. When the portable data store 118 or the remotedata server 112 are used to store account information, a user may beable to use the authentication manager 124 and the account informationon another client 103. To this end, the authentication manager 124 maybe, for example, downloaded, configured, and loaded automatically onanother client 103.

Security credentials may be shared among multiple users of theauthentication manager 124. As a non-limiting example, several users inan organization may share an online banking account. A first user maycreate a username and password for the account using the authenticationmanager 124. The first user may mark the account as shared and provide alist of users that are authorized to access the account, including asecond user. When the account is distributed to account data 130, 160,it is secured such that only the authorized users can access it. Whenthe second user next uses the authentication manager 124, the seconduser may be given the opportunity to synchronize the new account withaccount data 163 located in the portable data store 118 belonging to thesecond user or in some other location.

During the installation process, in one embodiment, the user may specifywhether the authentication manager 124 is to operate as a browser 121plug-in or as a standalone application. The authentication manager 124may be installed and configured for a plurality of browsers 121 such asFirefox®, Internet Explorer®, Safari®, and/or other browsers 121. Theauthentication manager 124 may also be configured for a plurality ofusers on the client 103.

When a user accesses a network site 140 with the browser 121 or anotherapplication, the authentication manager 124 determines whether thenetwork site 140 is associated with stored account information. If thenetwork site 140 is not associated with stored account information, thenthe authentication manager 124 may notify the user and may prompt theuser to provide security credentials if the user has an existingaccount. The user-provided security credentials may then be stored bythe authentication manager 124 in one or more of account data 130, 160,167.

Alternatively, or additionally, the authentication manager 124 mayassist the user in creating an account for the network site 140. Theaccount may be a one-time account, a first account for the user, or asecond or subsequent account for the user. The authentication manager124 may determine how to create an account for a network site 140 based,for example, on the structure of a form embedded within a network page145. Such a form may be defined in hypertext markup language (HTML),extensible markup language (XML), or some other language.

As a non-limiting example, the authentication manager 124 may identifyan account creation form when a submit input element on a network page145 is associated with text such as “Create Account.” The authenticationmanager 124 may also examine the URL for relevant keywords. As anothernon-limiting example, the authentication manager 124 may identify anaccount creation form when a challenge response test (e.g., a “Captcha”)is present. The authentication manager 124 may automatically identifyrequired fields for security credentials using, for example, inputelements on a network page 145 named “username,” “password,” or otheridentifiable names. In various embodiments, the authentication manager124 may have the user identify the account creation form and/or taginput elements of the form so that the authentication manager 124 mayaccurately identify how the account may be created with form filling.Such a list of tags can be stored in a configuration file 157 which maythen be uploaded to a configuration file server 109. There, theconfiguration file 157 can be accessed by other users using theauthentication manager 124 and used by them to simplify account creationon the network site 140 described by the configuration file 157.

In various embodiments, the authentication manager 124 may create theaccount in an automated way through methods other than form filling. Forexample, the authentication manager 124 may obtain a configuration file148 associated with the network site 140 from either the network pageserver 136 for the network site 140 or a configuration file server 109that may provide a configuration file 157 associated with the networksite 140. The configuration file 148, 157 may define one or more accountcreation endpoints 138 for the network site 140 where the authenticationmanager 124 may authenticate and/or create an account other than byfilling out a form. For example, the configuration file 148, 157 maydefine the URL, parameters, encoding, and/or other information requiredto create an account in an automated way through an account creationendpoint 138. In some embodiments, one account creation endpoint 138 maybe shared by multiple network sites 140 and/or network page servers 136.

The configuration file 148, 157 may also include a security credentialspecification associated with the network site 140. The securitycredential specification may specify a character set, minimum length,maximum length, and/or other parameters for usernames and/or passwords.The security credential specification may also specify minimum keylength, acceptable algorithms and formats, and/or other parametersapplicable to public key infrastructure or other types of securitycredentials. The authentication manager 124 may generate one or moresecurity credentials based on the security credential specification.

When the authentication manager 124 is creating an account by formfilling, the authentication manager 124 may prompt the user to supply asecurity credential specification so that the authentication manager 124may generate one or more security credentials to be filled in on theform. The user may see information regarding required attributes forsecurity credentials displayed on the network page 145 near the accountcreation form. The authentication manager 124 may provide optionsincluding, but not limited to, length of the security credential,directions to use a certain character set, directions to use at leastone number, directions to use at least one non-alphanumeric character,and other options. As a non-limiting example, the authentication manager124 may present a graphical interface to the user listing variousattributes that may be used in generating the security credentials. Sucha graphical interface may include, for example, checkboxes, radiobuttons, drop-down boxes, text fields, text areas, etc. The graphicalinterface may be preconfigured with default selections.

In various embodiments, when the authentication manager 124 is creatingan account by form filling, the authentication manager 124 may replace,for example, the normal user interaction in filling out the form with awizard interface. The wizard interface may omit tasks or fields that maybe done automatically by the authentication manager 124. However, thewizard interface may obtain input from the user in order to fill outfields such as “Captchas” and other challenge response tests. Althoughthe authentication manager 124 may be configured to fill out fieldspertaining to other personal information (e.g., name, date of birth,social security number, phone number, address, etc.), the authenticationmanager 124 may instead be configured to prompt the user for thatinformation. In various embodiments, the authentication manager 124 mayleave unrecognized form fields blank for the user to complete.

Accordingly, the authentication manager 124 and/or browser 121 sends anaccount creation request associated with the generated securitycredential to the network site 140. After the account creation requestis submitted, the account will either be created or not created for thenetwork site 140. The network site 140 typically provides a responsepage indicating whether the account creation was successful. Such anetwork page 145 may be parsed automatically by the authenticationmanager 124 or may be left for additional user input to theauthentication manager 124.

In some cases, the response page will include another form with anindication that there was a problem. As a non-limiting example, ausername field may be highlighted with an explanation that the specifiedusername was already taken. The authentication manager 124 may beconfigured to respond automatically to such requests and/or to seek userinput. Account creation responses through an authentication endpoint 139may be handled by the authentication manager 124 in an analogous way. Inone embodiment, the authentication manager 124 may simply assume thatthe account was created.

Responsive to account creation, the authentication manager 124 storesthe account information including, but not limited to, securitycredentials, URLs, and domain names associated with the account andnetwork site 140, in one or more of account data 130, 160, 163. Inparticular, the network site 140 or authentication endpoint 139 maypresent a trusted certificate from certificate data 154 during theaccount creation process. Information relating to this trustedcertificate, including domain name, certificate authority, and otherinformation from the certificate, may be stored with the accountinformation. The account information may consequently be marked asusable on a network site 140 corresponding to the domain name providedin the trusted certificate, or only for a network site 140 able topresent that specific certificate in higher assurance environments.Account information stored in any of account data 130, 160, 163 may bemanually or automatically copied by the authentication manager 124 toany other account data 130, 160, 163 so that the account information maybe mirrored across any two or more of account data 130, 160, 163.

For purposes of backup, the authentication manager 124 may be capable ofrendering a list of the stored account information in account data 130,160, 163 for viewing or printing. To facilitate viewing or printing, theauthentication manager 124 may be configured to generate human readableor printable security credentials using an appropriate character set.Alternatively, the authentication manager 124 may encode securitycredentials in a printable form using an encoding approach such as, forexample, UUencoding, BinHex, Multipurpose Internet Mail Extensions(MIME) encodings, Base64, and other encoding approaches.

When a stored account exists for a network site 140, the authenticationmanager 124 determines whether to provide the security credentials tothe network site 140. As a preliminary matter, the authenticationmanager 124 may require that the user be authenticated to theauthentication manager 124 by way of a master security credential suchas a password, presence of the portable data store 118 at the client103, biometric identification, native operating system identification,or some other authentication. Responsive to authentication, theauthentication manager 124 may decrypt the stored account data 130, 160,163. In some embodiments, the authentication manager 124 may be givenaccess to the stored account data 130, 160, 163 responsive to providinga master security credential. The authentication manager 124 thenverifies the identity of the network site 140.

Verifying the identity of the network site 140 may be performed, forexample, by comparing a domain name associated with a trustedcertificate provided by a network site 140 at the time of logon with thedomain name associated with the network site 140 in the stored accountinformation. The authentication manager 124 may compare the domain nameassociated with the trusted certificate provided by the network site140, for example, with a domain name provided by a user, a domain nameinferred by heuristic analysis, or some other domain name, in order toidentify which stored account the network site 140 appears to resemble.Verifying the identity of the network site 140 through the use oftrusted certificates may be less susceptible to spoofing attacks than byverifying the identity merely through domain name service (DNS) nameresolution, for example, or comparing a stored domain name to what isdisplayed in the address bar of the browser 121.

If the network site 140 provides no certificate (e.g., authenticationunder HTTP) or if the certificate is not trusted (e.g., self-signed orissued by a certificate authority not considered to be trusted in thecertificate trust data 133), the authentication manager 124 may displaya warning to the user. In some cases, the user may accept the warningand continue. In some embodiments, the authentication manager 124 mayremember such characteristics and use them to aid in future identityverification of the network site 140. In other cases, the authenticationmanager 124 may identify a clear use of a spoofing attack or otherphishing attempt and provide additional warnings, disable authenticationat the particular network site 140, require reauthentication by the userto the authentication manager 124, and/or take other precautions.Additionally, by integrating the authentication manager 124 with a siteproviding reputation data for network sites 140 the authenticationmanager 124 can warn the user that a network site 140 is hostile.

The authentication manager 124 may additionally verify the identity ofthe network site 140 by other methods. One verification method maycomprise comparing the contents of the address bar in the browser 121with a stored URL or domain name. A second verification method maycomprise comparing contents of the HTTP headers sent by the accessednetwork site 140 with a stored URL or domain name. A third verificationmethod may comprise performing a reverse DNS look-up on an InternetProtocol (IP) address associated with the accessed network site 140 andcomparing that domain name with a stored URL or domain name. Otherverification methods may also be employed. More secure methods may beemployed prior to downgrading to less secure methods, and the user mayspecify acceptable methods of proving the identity of network sites 140.

Once the identity of a network site 140 is verified, the authenticationmanager 124 may provide the security credentials to the network site 140automatically through an authentication endpoint 139 or may obtain userconfirmation. If the authentication manager 124 is configured to obtainuser input, the authentication manager 124 may render a button or otheruser interface feature in or on top of the browser 121 to obtainconfirmation.

When no authentication endpoint 139 is defined for a network site 140,the authentication manager 124 may be configured to detect whether anauthentication form is presented. The authentication manager 124 mayexamine the network page 145 for elements such as a submit input elementassociated with text such as “Log In,” input fields matching “username”and/or “password,” fields using the password type, and other identifyingelements. The authentication manager 124 may also examine the URL forrelevant keywords. In some embodiments, the authentication manager 124may store a URL associated with the network site 140 in account data130, 160, 163 which may be used for authentication. The authenticationmanager 124 may provide the security credentials to the network site 140by form filling. The submission of such a form may be automatic or maybe subject to user input such as selection of a “Submit” or “Log In”button or other user interface element.

Turning now to FIG. 2, shown is an example of a network page 145(FIG. 1) rendered by a browser 121 (FIG. 1) executed in a client 103(FIG. 1) in the networked environment 100 (FIG. 1) according to variousembodiments of the present disclosure. In this example, the user mayhave entered, or may have been automatically redirected to, the URL“https://www.e-retailer.site/,” which is displayed in the address bar203 of the browser 121. The network page 145 provided by the networksite 140 (FIG. 1) in response to the URL includes an authentication formhaving a username field 206, a password field 209, and a submit button212.

The browser 121 includes a security indication 215 that indicates thatthe network site 140 has presented a trusted certificate and thecommunication between the client 103 and the server 106 (FIG. 1) isbeing encrypted. In FIG. 2, the authentication manager 124 (FIG. 1) hasverified the identity of the network site 140 and is presenting anauthentication button 218. The authentication button 218 indicates thataccount information associated with the network site 140 is stored inaccount data 130, 160, 163.

Once a user selects the authentication button 218, the authenticationmanager 124 may fill in the username field 206 and the password field209. The authentication manager 124 may also automatically submit thelogon request by programmatically pressing the submit button 212. Insome embodiments, the username field 206 and password field 209 may beprefilled automatically with the security credential upon verificationof the identity of the network site 140. The security credentials may beshown as place holding characters or as plain text. Alternatively, if,for example, an authentication endpoint 139 (FIG. 1) is defined, theauthentication manager 124 may authenticate in the background. In such acase, the authentication manager 124 may give an indication of successor failure and may provide another authentication button 218 in order tolog out of the network site 140. If multiple user accounts are presentfor the network site 140, the authentication manager 124 may provide adrop-down box or other user interface element allowing the user toselect one of the accounts for authentication.

Referring next to FIG. 3, shown is another example of a network page 145(FIG. 1) rendered by a browser 121 (FIG. 1) executed in a client 103(FIG. 1) in the networked environment 100 (FIG. 1) according to variousembodiments of the present disclosure. In this example, the user mayhave entered, or may have been automatically redirected to, a differentURL such as “https://www.e-retailer.site.hackersrus.yz/,” which isdisplayed in the address bar 203 (FIG. 2) of the browser 121. Thenetwork page 145 provided by the network site 140 (FIG. 1) in responseto the URL includes an authentication form having a username field 206(FIG. 2), a password field 209 (FIG. 2), and a submit button 212 (FIG.2).

FIG. 3 represents an example of a common phishing scheme, where anetwork page 145 is presented by a fraudulent network site 140 having alook-and-feel that is identical or nearly identical to the network page145 presented by the legitimate network site 140. See FIG. 2. Althoughthe URL in this example includes the domain name of the legitimatenetwork site 140, the URL is not identical and is in fact a subdomain of“hackersrus.yz.” In this case, the authentication manager 124 (FIG. 1)cannot verify the identity of the network site 140 by way of the URLpresented in the address bar 203 because the domain name in the URL isnot a subdomain of, or identical to, the stored domain name“e-retailer.site” or “www.e-retailer.site.”

The network site 140 in FIG. 3 cannot be identified additionally becausethe network site 140 has not presented a trusted certificate as thesecurity indication 215 (FIG. 2) is absent. Various phishing attacks mayinvolve presenting a trusted certificate associated with the name ofsome other network site 140 or a real certificate for the fraudulentnetwork site 140. Other phishing attacks may involve substituting asecurity indication 215 that is faked. The authentication manager 124may avoid such attacks because it is not deceived by graphicalappearances but instead may examine the network page 145 and certificatedata received behind the scenes by the browser 121. The authenticationmanager 124 determines that this network site 140 in FIG. 3 has nostored security credentials. Thus, in this non-limiting example, theauthentication manager 124 presents an information button 303 in placeof an authentication button 218 (FIG. 2) that states “No Log InInformation Found.”

In some embodiments, the authentication manager 124 may employ aheuristic analysis of the network page 145 and/or reputation data toidentify fraudulent sites proactively. For example, the authenticationmanager 124 may perform a heuristic analysis to determine whether anetwork page includes a logon form that is a fraudulent copy of a logonform associated with a stored domain name. In such cases, theauthentication manager 124 may provide a warning to the user.Additionally, if the user were to request that the authenticationmanager 124 provide the security credentials used for a legitimatenetwork site 140 to a fraudulent network site 140 (e.g., if the domainname of a trusted certificate of the fraudulent network site 140 doesnot match the stored domain name associated with the legitimate networksite 140), the authentication manager 124 may generate a warning.

Moving on to FIG. 4, shown is an example of a network page 145 (FIG. 1)rendered by a browser 121 (FIG. 1) executed in a client 103 (FIG. 1) inthe networked environment 100 (FIG. 1) according to various embodimentsof the present disclosure. In this example, the browser 121 appearsidentical to that depicted in FIG. 2, except that the authenticationmanager 124 (FIG. 1) has provided an information button 303 (FIG. 3) inplace of an authentication button 218 (FIG. 2). The address bar 203(FIG. 2) appears to depict the URL of the legitimate network site 140(FIG. 1). However, the secure certificate was issued by an untrustedcertificate authority.

The inconsistency may be explained by spoofing attacks according tovarious methods such as, for example, a man-in-the-middle attack andother attacks. As a non-limiting example, the client 103 may have beenprovided misbehaving and/or compromised DNS servers through the dynamichost configuration protocol (DHCP). The misbehaving DNS servers may beconfigured to give inaccurate domain name information. By contrast,malicious users are less likely to be able to compromise a trustedcertificate authority because public key infrastructure is used. Here,the authentication manager 124 has determined that a network site 140 isnot verified and has not provided the security credentials. An ordinaryuser, however, may have been misled and supplied the securitycredentials to the fraudulent network site 140.

In some cases, the inconsistency may result from a legitimate networksite 140 changing its certificate provider. The authentication manager124 may include a configuration setting to enable a warning when thecertificate authority signing the secure certificate for a network site140 changes from the certificate authority that issued the securecertificate that the authentication manager 124 received when thesecurity credential was previously created or stored for the networksite 140.

With reference to FIG. 5, shown is a flowchart that provides one exampleof the operation of a portion of the authentication manager 124 (FIG. 1)according to various embodiments. It is understood that the flowchart ofFIG. 5 provides merely an example of the many different types offunctional arrangements that may be employed to implement the operationof the portion of the authentication manager 124 as described herein. Asan alternative, the flowchart of FIG. 5 may be viewed as depicting anexample of steps of a method implemented in the client 103 (FIG. 1)according to one or more embodiments.

Beginning with box 503, the authentication manager 124 obtains a networkpage 145 (FIG. 1) from a network site 140 (FIG. 1) in response to arequest by a user. In various embodiments, the network page 145 may beobtained through operation of the browser 121 (FIG. 1). Next, in box506, the authentication manager 124 determines whether the network site140 requires authentication. This determination may be based, forexample, on the presence of an authentication form on the network page145 or some other network page 145 on the network site 140, the presenceof a configuration file 148, 157 (FIG. 1), on user input, or on otherfactors. If authentication is not required by the network site 140, thecontrol flow of the authentication manager 124 stops.

After determining that a network site 140 requires authentication, theauthentication manager 124 proceeds to box 509. In box 509, theauthentication manager 124 determines whether the identity of thenetwork site 140 can be verified. This verification may involve, forexample, examination of a domain name associated with a trustedcertificate received in connection with the network page 145.

If the authentication manager 124 cannot verify the identity of thenetwork site 140, the authentication manager 124 moves to box 512 andwarns the user that the identity of the site cannot be verified and/ornotifies the user that no stored account information can be found. Next,the authentication manager 124 determines in box 515 whether the userhas indicated to proceed with authentication nonetheless using otherstored account information. In some embodiments, the authenticationmanager 124 may preclude the user from proceeding with authentication.If the user has not indicated to proceed, the control flow of theauthentication manager 124 stops. If the user has indicated to proceedin box 515, the authentication manager 124 moves to box 518. If in box509 the identity of the network site 140 has been verified, theauthentication manager 124 moves also to box 518.

In box 518, the authentication manager 124 determines whether an accountexists in account data 130, 160, 163 (FIG. 1) for the network site 140.This determination may be made by comparing the domain name associatedwith the request with stored domain names in account data 130, 160, 163.Additionally, the user may provide a domain name to the authenticationmanager 124 which the user believes to correspond to the network site140 in order to locate a stored account. If the authentication manager124 determines that an account does not exist, the authenticationmanager 124 proceeds to box 519 and offers to create an account for theuser. Account creation is covered in more detail by the flowchart ofFIG. 6. Moreover, additional accounts for a same network site 140 may becreated by the authentication manager 124 in response to user input.

Next, in box 521, the authentication manager 124 determines whether anauthentication endpoint 139 (FIG. 1) has been defined for the networkpage 145 or network site 140. This may involve examining, if they exist,configuration files 148, 157 (FIG. 1). If an authentication endpoint 139has not been defined, the authentication manager 124 moves to box 524and provides the account parameters, including security credentials, byform filling. The authentication manager 124 may send the accountparameters to the network site 140 or may merely allow the user tosubmit the form. The control flow of the authentication manager 124 thenstops.

If in box 521 the authentication manager 124 determines that anauthentication endpoint 139 has been defined, the authentication manager124 proceeds to box 527 and provides the account parameters by way ofthe authentication endpoint 139. The authentication manager 124 may sendthe account parameters to the network site 140 or wait for user inputfor approval. The control flow of the authentication manager 124 thenstops.

Turning now to FIG. 6, shown is a flowchart that provides one example ofthe operation of another portion of the authentication manager 124(FIG. 1) according to various embodiments. It is understood that theflowchart of FIG. 6 provides merely an example of the many differenttypes of functional arrangements that may be employed to implement theoperation of the portion of the authentication manager 124 as describedherein. As an alternative, the flowchart of FIG. 6 may be viewed asdepicting an example of steps of a method implemented in the client 103(FIG. 1) according to one or more embodiments.

Beginning with box 603, the authentication manager 124 determineswhether there is a configuration file 148, 157 (FIG. 1) for the networksite 140 (FIG. 1). If there is not, the authentication manager 124 movesto box 606 and obtains account creation parameters from the user. Theparameters may relate, for example, to length of a password, permissiblecharacters, required characters, etc.

Then, in box 609, the authentication manager 124 uses form filling tocreate the account on the network site 140. User input may be necessaryto submit the form in some embodiments, or the account creation requestmay be submitted automatically. If the account creation request resultsin failure, the authentication manager 124 may return to box 606 orleave the account creation up to the user. Next, in box 612, theauthentication manager 124 stores account parameters in one or more ofaccount data 130, 160, 163 (FIG. 1). The control flow of theauthentication manager 124 then stops.

If the authentication manager 124 determines in box 603 that aconfiguration file 148, 157 exists for the network site 140, theauthentication manager 124 moves to box 615 and obtains account creationparameters from a configuration file 148, 157. Then, in box 618, theauthentication manager 124 determines whether an account creationendpoint 138 (FIG. 1) is defined. If no account creation endpoint 138 isdefined, the authentication manager 124 moves to box 609.

Then, in box 609, the authentication manager 124 uses form filling tocreate the account on the network site 140. User input may be necessaryto submit the form in some embodiments, or the account creation requestmay be submitted automatically. If the account creation request resultsin failure, the authentication manager 124 may return to box 606 orleave the account creation up to the user. Next, in box 612, theauthentication manager 124 stores account parameters in one or more ofaccount data 130, 160, 163. The control flow of the authenticationmanager 124 then stops.

If in box 618, the authentication manager 124 determines that an accountcreation endpoint 138 has been defined, the authentication manager 124proceeds to box 621 and uses the account creation endpoint 138 to createan account on the site. Next, in box 612, the authentication manager 124stores account parameters in one or more of account data 130, 160, 163.The authentication manager 124 then ends.

Referring next to FIG. 7, shown is a schematic block diagram of theclient 103 (FIG. 1) according to one embodiment of the presentdisclosure. The client 103 includes a processor circuit, for example,having a processor 703 and a memory 706, both of which are coupled to alocal interface 709. The local interface 709 may comprise, for example,a data bus with an accompanying address/control bus or other busstructure as can be appreciated.

Stored in the memory 706 are both data and several components that areexecutable by the processor 703. In particular, stored in the memory 706and executable by the processor 703 are a browser 121 (FIG. 1),authentication manager 124 (FIG. 1), and potentially other applications.Also stored in the memory 706 may be a data store 127 (FIG. 1) and otherdata. In addition, an operating system may be stored in the memory 706and executable by the processor 703.

It is understood that there may be other applications that are stored inthe memory 706 and are executable by the processors 703 as can beappreciated. Where any component discussed herein is implemented in theform of software, any one of a number of programming languages may beemployed such as, for example, C, C++, C#, Objective C, Java, JavaScript, Perl, Python, Ruby, Flash, or other programming languages.

A number of software components are stored in the memory 706 and areexecutable by the processor 703. In this respect, the term “executable”means a program file that is in a form that can ultimately be run by theprocessor 703. Examples of executable programs may be, for example, acompiled program that can be translated into machine code in a formatthat can be loaded into a random access portion of the memory 706 andrun by the processor 703, source code that may be expressed in properformat such as object code that is capable of being loaded into a randomaccess portion of the memory 706 and executed by the processor 703, orsource code that may be interpreted by another executable program togenerate instructions in a random access portion of the memory 706 to beexecuted by the processor 703, etc. An executable program may be storedin any portion or component of the memory 706 including, for example,random access memory (RAM), read-only memory (ROM), hard drive,solid-state drive, USB flash drive, memory card, optical disc such ascompact disc (CD) or digital versatile disc (DVD), floppy disk, magnetictape, or other memory components.

The memory 706 is defined herein as including both volatile andnonvolatile memory and data storage components. Volatile components arethose that do not retain data values upon loss of power. Nonvolatilecomponents are those that retain data upon a loss of power. Thus, thememory 706 may comprise, for example, random access memory (RAM),read-only memory (ROM), hard disk drives, solid-state drives, USB flashdrives, memory cards accessed via a memory card reader, floppy disksaccessed via an associated floppy disk drive, optical discs accessed viaan optical disc drive, magnetic tapes accessed via an appropriate tapedrive, and/or other memory components, or a combination of any two ormore of these memory components. In addition, the RAM may comprise, forexample, static random access memory (SRAM), dynamic random accessmemory (DRAM), or magnetic random access memory (MRAM) and other suchdevices. The ROM may comprise, for example, a programmable read-onlymemory (PROM), an erasable programmable read-only memory (EPROM), anelectrically erasable programmable read-only memory (EEPROM), or otherlike memory device.

Also, the processor 703 may represent multiple processors and the memory706 may represent multiple memories that operate in parallel processingcircuits, respectively. In such a case, the local interface 709 may bean appropriate network that facilitates communication between any two ofthe multiple processors 703, between any processor 703 and any of thememories 706, or between any two of the memories 706, etc. The localinterface 709 may comprise additional systems designed to coordinatethis communication, including, for example, performing load balancing.The processor 703 may be of electrical or of some other availableconstruction.

Although the browser 121, authentication manager 124, and other varioussystems described herein may be embodied in software or code executed bygeneral purpose hardware as discussed above, as an alternative the samemay also be embodied in dedicated hardware or a combination ofsoftware/general purpose hardware and dedicated hardware. If embodied indedicated hardware, each can be implemented as a circuit or statemachine that employs any one of or a combination of a number oftechnologies. These technologies may include, but are not limited to,discrete logic circuits having logic gates for implementing variouslogic functions upon an application of one or more data signals,application specific integrated circuits having appropriate logic gates,or other components, etc. Such technologies are generally well known bythose skilled in the art and, consequently, are not described in detailherein.

The flowcharts of FIGS. 5 and 6 show the functionality and operation ofan implementation of portions of the authentication manager 124. Ifembodied in software, each block may represent a module, segment, orportion of code that comprises program instructions to implement thespecified logical function(s). The program instructions may be embodiedin the form of source code that comprises human-readable statementswritten in a programming language, or machine code that comprisesnumerical instructions recognizable by a suitable execution system suchas a processor in a computer system or other system. The machine codemay be converted from the source code, etc. If embodied in hardware,each block may represent a circuit or a number of interconnectedcircuits to implement the specified logical function(s).

Although the flowcharts of FIGS. 5 and 6 show a specific order ofexecution, it is understood that the order of execution may differ fromthat which is depicted. For example, the order of execution of two ormore blocks may be scrambled relative to the order shown. Also, two ormore blocks shown in succession in FIGS. 5 and 6 may be executedconcurrently or with partial concurrence. In addition, any number ofcounters, state variables, warning semaphores, or messages might beadded to the logical flow described herein, for purposes of enhancedutility, accounting, performance measurement, or providingtroubleshooting aids, etc. It is understood that all such variations arewithin the scope of the present disclosure.

Also, any logic or application described herein, including the browser121 and the authentication manager 124, that comprises software or codecan be embodied in any computer-readable medium for use by or inconnection with an instruction execution system such as, for example, aprocessor in a computer system or other system. In this sense, the logicmay comprise, for example, statements including instructions anddeclarations that can be fetched from the computer-readable medium andexecuted by the instruction execution system. In the context of thepresent disclosure, a “computer-readable medium” can be any medium thatcan contain, store, or maintain the logic or application describedherein for use by or in connection with the instruction executionsystem. The computer readable medium can comprise any one of manyphysical media such as, for example, electronic, magnetic, optical,electromagnetic, infrared, or semiconductor media. More specificexamples of a suitable computer-readable medium would include, but arenot limited to, magnetic tapes, magnetic floppy diskettes, magnetic harddrives, memory cards, solid-state drives, USB flash drives, or opticaldiscs. Also, the computer-readable medium may be a random access memory(RAM) including, for example, static random access memory (SRAM) anddynamic random access memory (DRAM), or magnetic random access memory(MRAM). In addition, the computer-readable medium may be a read-onlymemory (ROM), a programmable read-only memory (PROM), an erasableprogrammable read-only memory (EPROM), an electrically erasableprogrammable read-only memory (EEPROM), or other type of memory device.

It should be emphasized that the above-described embodiments of thepresent disclosure are merely possible examples of implementations setforth for a clear understanding of the principles of the disclosure.Many variations and modifications may be made to the above-describedembodiment(s) without departing substantially from the spirit andprinciples of the disclosure. All such modifications and variations areintended to be included herein within the scope of this disclosure andprotected by the following claims.

Therefore, the following is claimed:
 1. A system, comprising: a clientcomputing device; and an authentication manager executable in the clientcomputing device, wherein when executed the authentication managercauses the client computing device to at least: perform an identityverification on a network site; determine that a particular portabledata store is present in the client computing device; read a securitycredential from the particular portable data store; and automaticallysend data encoding the security credential to the network site.
 2. Thesystem of claim 1, wherein the particular portable data store stores aplurality of security credentials corresponding to a plurality ofnetwork sites.
 3. The system of claim 1, wherein the particular portabledata store is removably attached to the client computing device.
 4. Thesystem of claim 1, wherein the security credential is stored by theparticular portable data store in an encrypted format.
 5. The system ofclaim 1, wherein the particular portable data store includes a biometricrecognition device, and the particular portable data store is configuredto provide access to the security credential in response to thebiometric recognition device authenticating a user.
 6. The system ofclaim 5, wherein the biometric recognition device comprises afingerprint scanner.
 7. The system of claim 1, wherein the particularportable data store comprises hardware configured to receive auser-provided password, and access by the authentication manager to thesecurity credential is provided in response to the user-providedpassword being entered.
 8. The system of claim 1, wherein theauthentication manager is stored on the particular portable data storeand is executed by the client computing device in response to theparticular portable data store being attached to the client computingdevice.
 9. A method, comprising: receiving, via an authenticationmanager executed by a client, a configuration file including a securitycredential specification for a network site; extracting, via theauthentication manager executed by the client, a maximum credentiallength and a character set from the security credential specification;and automatically generating, via the authentication manager executed bythe client, a security credential for the network site based at least inpart on the maximum credential length and the character set allowed bythe security credential specification.
 10. The method of claim 9,further comprising sharing, via the authentication manager executed bythe client, the security credential with a plurality of authorizedusers.
 11. The method of claim 9, wherein the configuration file isreceived from a third-party configuration file server.
 12. The method ofclaim 9, further comprising: verifying, via the authentication managerexecuted by the client, an identity of the network site; retrieving, viathe authentication manager executed by the client, the securitycredential from a data store; and automatically providing, via theauthentication manager executed by the client, data encoding thesecurity credential to the network site in order to authenticate. 13.The method of claim 9, further comprising: determining, via theauthentication manager executed by the client, an account creationendpoint for the network site specified in the configuration file; andautomatically creating, via the authentication manager executed by theclient, an account with the network site having the security credentialvia the account creation endpoint.
 14. The method of claim 9, furthercomprising storing, via the authentication manager executed by theclient, the security credential in a portable data store attached to theclient.
 15. The method of claim 14, wherein the authentication manageris stored on and executed from the portable data store.
 16. The methodof claim 9, further comprising automatically filling, via theauthentication manager executed by the client, the security credentialin an account creation form for the network site.
 17. The method ofclaim 16, further comprising: receiving, via the authentication managerexecuted by the client, a user tag of an input element in the accountcreation form; storing, via the authentication manager executed by theclient, the user tag in another configuration file; and sending, via theauthentication manager executed by the client, the other configurationfile to a configuration file server accessible by a plurality of otherinstances of the authentication manager associated with a plurality ofother users.
 18. A non-transitory computer-readable medium embodying anauthentication manager executable in a client computing device, whereinwhen executed the authentication manager causes the client computingdevice to at least: receive a configuration file including a securitycredential specification for a network site; extract a parameter fromthe security credential specification; automatically generate a securitycredential for the network site based at least in part on the parameterfrom the security credential specification; automatically create anaccount for the network site using the security credential; and storethe security credential in a particular portable data store removablyattached to the client computing device.
 19. The non-transitorycomputer-readable medium of claim 18, wherein when executed theauthentication manager further causes the client computing device to atleast: perform an identity verification on the network site; determinethat the particular portable data store is present in the clientcomputing device; read the security credential from the particularportable data store; and automatically send data encoding the securitycredential to the network site.
 20. The non-transitory computer-readablemedium of claim 18, wherein the parameter comprises at least one of: amaximum credential length or a character set.